home *** CD-ROM | disk | FTP | other *** search
- +++++++++++++++++++++++++++++++++ ++++
- ++++++++++++++++++++++++++++++++++++ +++++++
- +++++++++++++++++++++++++++++++++++++ ++++++++
- ++++++++++++++++++++++++++++++++++++ ++++++++
- ++++++++
- ++++++++
- +++++++++++++++++++++++++++ ++++++++
- +++++++++++++++++++++++++++++ ++++++++
- +++++++++++++++++++++++++++++ ++++++++
- +++++++++++++++++++++++++++ ++++++++
- ++++++++
- ++++++++
- ++++++++++++++++++++++++++++++++++++ ++++++++
- +++++++++++++++++++++++++++++++++++++ ++++++++
- ++++++++++++++++++++++++++++++++++++ ++++++++
- +++++++++++++++++++++++++++++++++ +++++
-
- (C)Copyright 1993-1996 SysKonnect,
- a business unit of Schneider & Koch & Co. Datensysteme GmbH.
- All rights reserved
- ==========================================================================
-
- SKFINT.TXT
-
- Readme File for Windows NT NDIS3 Driver for SK-NET FDDI ISA Adapters
- Subject: SKFINT.SYS NDIS3 Driver corresponding to the NDIS 3.0
- Specification as delivered with Windows NT.
-
-
-
- Version / Date / Author of this file: v2.10 / 28-Mar-1996 / SW
- Version / Date / Author of the referred subject: v2.32 / 28-Mar-1996 / SW
-
- This file contains
- (1) Overview
- (2) Required files
- (3) Installation instructions
- (4) Troubleshooting
- (5) History
-
- ===============================================================================
-
-
- (1) OVERVIEW
- ============
-
- This README explains how to install the SKFINT.SYS driver on a
- Windows NT workstation or server.
- ***
-
-
- (2) REQUIRED FILES
- ==================
-
- In a single directory
-
- - OEMNADSK.HLP Help file for SK-NET drivers
-
- - OEMNADSK.DLL Dialogs for SK-NET drivers
-
- - OEMSETUP.INF Setup script for the driver
-
- - SKFINT.SYS The driver
- ***
-
-
- (3) INSTALLATION INSTRUCTIONS
- =============================
-
- NOTE: On an EISA machine, the SK-NET FDDI ISA Adapter should be
- configured using the appropriate EISA configuration file.
-
- Step 1: Start Windows NT.
-
- Step 2: Open the CONTROL PANEL.
-
- Step 3: Start NETWORK.
-
- Step 4: Select ADD ADAPTER.
-
- Step 5: Select <OTHER>.
-
- Step 6: Type in the path to OEMSETUP.INF.
-
- Step 7: Select the driver presented and select the appropriate configuration.
- Then choose OK and restart your system.
- ***
-
-
- (4) TROUBLESHOOTING
- ===================
-
- If you encounter problems using the SK-NET FDDI ISA Adapter, please
- re-read carefully the instructions above and the documentation supplied
- with the system.
-
- If this does not help, please send us a description of the problems you have.
-
- Also refer to your system log file (using the event viewer) and check
- it for entries from SKFINT.
-
- The last 5 DWORDs of the logging data are:
-
- - Slot number (-1 if the adapter is not EISA-configured),
-
- - Interrupt number,
-
- - Dma channel,
-
- - Base I/O port, and
-
- - Vendor code (3 bytes) / adapter id (1 byte)
-
- of the adapter that caused the error.
-
- Follows a list of some events, possible reasons (may be incomplete)
- and suggestions to fix your problem.
-
- Event ID: 5001 - Could not allocate the resources necessary
- for operation.
- Reason(s): Not enough RAM or pagefile too small.
- Help: ...
-
- ---------------
-
- Event ID: 5003 - Could not find an adapter.
- Reason(s): Wrong slot or IO Port.
- Adapter physically not installed.
- System configuration information invalid.
- Help: Check slot/port settings.
- Check if adapter is physically present.
- Check system configuration.
-
- ---------------
-
- Event ID: 5004 - Could not connect to the interrupt number supplied.
- Reason(s): The selected interrupt is already in use.
- Help: Select free interrupt.
-
- ---------------
-
- Event ID: 5007 - Timed out during an operation.
- Reason(s): Wrong interrupt, DMA channel or base address.
- Cable not connected.
- Help: Start a driver under e.g. DOS (with the same resource usage)
- and see if it works.
- Check cabling.
-
- ---------------
-
- Event ID: 5009 - Does not support the configuration supplied.
- Reason(s): Invalid IRQ or DMA given.
- Help: Check configuration.
-
- ---------------
-
- Event ID: 5012 - The I/O base address supplied does not match
- the jumpers on the adapter.
- Reason(s): Jumper settings and software configuration conflict.
- Help: Check jumper settings against software configuration.
-
-
- If your special problem is not listed or the error persists, please
- send us your system log file or at least the event id number and the
- logging data (as dwords) of the entries made by SKFINT.
- ***
-
-
- (5) HISTORY
- ===========
-
- v2.00 Rev. A
- - OID_GEN_DRIVER_VERSION now returns NDIS version (3.00) instead of driver
- version.
- - On EISA and MCA machines the installation script inserts the keyword
- <BusNumber> into the registry.
- - More memory is used as receive buffer to reduce overflows.
- v2.00 Rev. C
- - Fixed test for successful memory allocation.
- v2.00 Rev. D
- - Runs on multiprocessor systems.
- - LINK_SPEED reporting corrected.
- v2.01
- - Rejecting unsupported filters.
- v2.10
- - Included EnhancedNonLlc mode.
- - Implemented limited promiscuous mode (receive all non-LLC frames).
- This may be disabled by setting <LimitPromiscuous> to 1 in the registry.
- - SBA/ESS added
- - Runs stable on multiprocessor systems.
- v2.10 Rev. C
- - Fixes a problem with string parameter parsing (may prevent SBA/ESS from
- starting)
- v2.20
- - Fixes OID problems seen with the new NDIS tester.
- v2.30
- - Fixed system crashing due to TCPIP reentrancy problems (stack
- overflow).
- - No longer writing a "Timeout" error log entry under heavy load.
- - Double receive buffers allow parallel execution of DMA and receive
- indication.
- - Reset mechanism; both "soft" (caused by protocol) and "hard" (caused by
- timeout watchdog).
- v2.31
- - Software or hardware failure detected by driver caused the driver to
- stop (endless software loop).
- - Sender could deadlock when network load was heavy.
- v2.32
- - Fixed lookahead length problems (OID_GEN_CURRENT_LOOKAHEAD) experienced
- with new NDIS Tester (NCT).
- ***
-
- *** End of information file ***